rustdoc: Stop unconditionally evaluating the initializer of associated consts#151232
Conversation
ab8d394 to
1aacbfc
Compare
|
This should theoretically have a positive impact on performance. @bors try @rust-timer queue |
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
rustdoc: Stop evaluating associated consts
This comment has been minimized.
This comment has been minimized.
|
Finished benchmarking commit (9e129b1): comparison URL. Overall result: ✅ improvements - no action neededBenchmarking this pull request means it may be perf-sensitive – we'll automatically label it not fit for rolling up. You can override this, but we strongly advise not to, due to possible changes in compiler perf. @bors rollup=never Instruction countOur most reliable metric. Used to determine the overall result above. However, even this metric can be noisy.
Max RSS (memory usage)Results (primary -2.2%, secondary -4.8%)A less reliable metric. May be of interest, but not used to determine the overall result above.
CyclesResults (primary -1.5%, secondary -19.1%)A less reliable metric. May be of interest, but not used to determine the overall result above.
Binary sizeThis benchmark run did not return any relevant results for this metric. Bootstrap: 472.76s -> 472.975s (0.05%) |
1aacbfc to
1175147
Compare
|
Nice! And simple enough to backport :) |
1175147 to
ac8e850
Compare
|
CI was green but I've just force-pushed again to tweak the commit message slightly. r? yotamofek @bors r=yotamofek |
|
Beta backport accepted as per #t-rustdoc > beta-nominated: #151232 @ 💬. |
…=fmease [beta] rustdoc: Stop unconditionally evaluating the initializer of associated consts Last minute beta backport of #151232 ([beta backport accepted](https://rust-lang.zulipchat.com/#narrow/channel/266220-t-rustdoc/topic/beta-nominated.3A.20.23151232/near/568543129)). Directly fixes #149635. Not part of some hypothetical future backport rollup because we're under time pressure as the release procedures have commenced already: https://forge.rust-lang.org/#current-release-versions, https://forge.rust-lang.org/release/process.html. r? fmease
This comment has been minimized.
This comment has been minimized.
What is this?This is an experimental post-merge analysis report that shows differences in test outcomes between the merged PR and its parent PR.Comparing 9f6cd6d (parent) -> fe98ddc (this PR) Test differencesShow 6 test diffsStage 1
Stage 2
Additionally, 2 doctest diffs were found. These are ignored, as they are noisy. Job group index Test dashboardRun cargo run --manifest-path src/ci/citool/Cargo.toml -- \
test-dashboard fe98ddcfcfb6f185dbf4adeaf439d8a756da0273 --output-dir test-dashboardAnd then open Job duration changes
How to interpret the job duration changes?Job durations can vary a lot, based on the actual runner instance |
|
Finished benchmarking commit (fe98ddc): comparison URL. Overall result: ✅ improvements - no action needed@rustbot label: -perf-regression Instruction countOur most reliable metric. Used to determine the overall result above. However, even this metric can be noisy.
Max RSS (memory usage)Results (primary -0.9%, secondary -4.5%)A less reliable metric. May be of interest, but not used to determine the overall result above.
CyclesResults (primary -2.1%, secondary -14.9%)A less reliable metric. May be of interest, but not used to determine the overall result above.
Binary sizeResults (primary 0.1%, secondary 0.1%)A less reliable metric. May be of interest, but not used to determine the overall result above.
Bootstrap: 472.543s -> 473.229s (0.15%) |
See the descriptions of the added tests for details.
Fixes #131625.
Fixes [after beta-1.93 backport] #149635.
Fixes #150312.
Supersedes #150629 IINM.
CC @cuviper (#149635 (comment))
r? @GuillaumeGomez or @yotamofek (#150629)